Value consistency
| Characteristic Name: | Value consistency |
| Dimension: | Consistency |
| Description: | Data values are consistent and do not provide conflicting or heterogeneous instances |
| Granularity: | Element |
| Implementation Type: | Rule-based approach |
| Characteristic Type: | Declarative |
Verification Metric:
| The number of inconsistent data values reported in an attribute per thousand records |
GuidelinesExamplesDefinitons
The implementation guidelines are guidelines to follow in regard to the characteristic. The scenarios are examples of the implementation
| Guidelines: | Scenario: |
|---|---|
| For critical data elements provide standard classifications (values lists) for data entry interfaces and restrict arbitrary values across the system | (1) Country, city are taken from a standard list. (2) Generally accepted industry classifications are used to analyse customers industry wise (Education, Banking & Finance, Medical, Manufacturing……. |
| When data elements are combined for specific identification/management/accounting purposes, standardise such combinations and use them across the system. | (1) Customer and sales order are combined for identification purposes (2) Costs of wastage are associated with individual orders they are incurred and managed. |
| Define data attributes in such a way that data values are atomic and hence consistency can be maintained for any form of aggregation or consolidation | Name is divided into first name Middle name and Last Name |
| Maintain consistency in using unit of measures across different tables and different data bases | Sales price is in $ in Sales table and Accounts receivable ledger |
Validation Metric:
| How mature is the creation and implementation of the DQ rules to maintain value consistency |
These are examples of how the characteristic might occur in a database.
| Example: | Source: |
|---|---|
| School admin: a student’s date of birth has the same value and format in the school register as that stored within the Student database. | N. Askham, et al., “The Six Primary Dimensions for Data Quality Assessment: Defining Data Quality Dimensions”, DAMA UK Working Group, 2013. |
| For example, data are inconsistent when it is documented that a male patient has had a hysterectomy. | B. Cassidy, et al., “Practice Brief: Data Quality Management Model” in Journal of AHIMA, 1998, 69(6). |
| the name of the city and the postal code should be consistent. This can be enabled by entering just the postal code and filling in the name of the city systematically through the use of referential integrity with a postal code table | Y. Lee, et al., “Journey to Data Quality”, Massachusetts Institute of Technology, 2006. |
| the data values ST Louis and Saint Louis may both refer to the same city. However, the recordings are inconsistent, and thus at least one of them is inaccurate. | J. E. Olson, “Data Quality: The Accuracy Dimension”, Morgan Kaufmann Publishers, 9 January 2003. |
The Definitions are examples of the characteristic that appear in the sources provided.
| Definition: | Source: |
|---|---|
| Domain Level: The data values persist from a particular data element of the data source to another data element in a second data source. Consistency can also reflect the regular use of standardized values, articularly in descriptive elements. Entity Level: The entity’s domains and domain values either persist intact or can be logically linked from one data source to another data source. Consistency can also reflect the regular use of standardized values particularly in descriptive domains. | B. BYRNE, J. K., D. MCCARTY, G. SAUTER, H. SMITH, P WORCESTER 2008. The information perspective of SOA design Part 6:The value of applying the data quality analysis pattern in SOA. IBM corporation. |
| Determines the extent to which distinct data instances provide nonconflicting information about the same underlying data object. For example, the salary range for level 4 employees must be between $40,000 and $65,000. | G. GATLING, C. B., R. CHAMPLIN, H. STEFANI, G. WEIGEL 2007. Enterprise Information Management with SAP, Boston, Galileo Press Inc. |
| Data is consistent if it doesn’t convey heterogeneity, neither in contents nor in form – anti examples: Order.Payment. Type = ‘Check’; Order. Payment. CreditCard_Nr = 4252… (inconsistency in contents); Order.requested_by: ‘European Central Bank’;Order.delivered_to: ‘ECB’ (inconsistency in form,because in the first case the customer is identified by the full name, while in the second case the customer’s acronym is used). | KIMBALL, R. & CASERTA, J. 2004. The data warehouse ETL toolkit: practical techniques for extracting. Cleaning, Conforming, and Delivering, Digitized Format, originally published. |
| Consistency can be curiously simple or dangerously complex. In its most basic form, consistency refers to data values in one data set being consistent with values in another data set. Two data values drawn from separate data sets may be consistent with each other, yet both can be incorrect. | LOSHIN, D. 2001. Enterprise knowledge management: The data quality approach, Morgan Kaufmann Pub. |
| In its most basic form, consistency refers to data values in one data set being consistent with values in another data set. A strict definition of consistency specifies that two data values drawn from separate data sets must not conflict with each other, although consistency does not necessarily imply correctness. | LOSHIN, D. 2006. Monitoring Data quality Performance using Data Quality Metrics. Informatica Corporation. |
| Consistency, in popular usage, means that two or more things do not conflict with one another. This usage extends reasonably well to data values, although a bit of added discipline is desired. | REDMAN, T. C. 1997. Data quality for the information age, Artech House, Inc. |
Standards and regulatory compliance
| Characteristic Name: | Standards and regulatory compliance |
| Dimension: | Validity |
| Description: | All data processing activities should comply with the policies, procedures, standards, industry benchmark practices and all regulatory requirements that the organization is bound by |
| Granularity: | Information object |
| Implementation Type: | Process-based approach |
| Characteristic Type: | Usage |
Verification Metric:
| The number of tasks failed or under performed due non adherence of standards and regulations |
| The number of complaints received due to non adherence to standards and regulations |
GuidelinesExamplesDefinitons
The implementation guidelines are guidelines to follow in regard to the characteristic. The scenarios are examples of the implementation
| Guidelines: | Scenario: |
|---|---|
| Identify the policies, procedures, standards, benchmark practices and any regulatory requirements that an Information object is bound by | (1) Each person's compensation criteria must be determined in accordance with the Annuities Based on Retired or Retainer Pay law. |
| Ensure that all data processing activities are well defined and documented based on the policies, procedures, standards, benchmarks and regulatory requirements. | (1) Process of making a damage estimate is well defined based on industry benchmarks |
| Ensure that the application programs cater for standards and regulatory compliance | (1) A software program to make damage estimates which includes all benchmark data |
| Regularly monitor the data processing activities and identify the problems and inefficiencies so that the corrective and preventive actions can be taken. | (1) Frequent delays in time sheet approvals results in delayed payments |
| Signs should be standardised and universally used | (1) In the line efficiency report, low efficiency lines are indicated using a RED light while a green light indicates high efficiency |
| Relevant standard, procedures, policies and regulations should be communicated to the users effectively | (1) Providing a guidelines for signs |
| Ensure that proper conversion tables are maintained and used in converting attribute vales to different measurement bases. | (1) Metric conversion tables are used to convert lbs to kgs. |
Validation Metric:
| How mature is the process maintain the adherence to standards and regulations |
These are examples of how the characteristic might occur in a database.
| Example: | Source: |
|---|---|
| The age at entry to a UK primary & junior school is captured on the form for school applications. This is entered into a database and checked that it is between 4 and 11. If it were captured on the form as 14 or N/A it would be rejected as invalid. | N. Askham, et al., “The Six Primary Dimensions for Data Quality Assessment: Defining Data Quality Dimensions”, DAMA UK Working Group, 2013. |
The Definitions are examples of the characteristic that appear in the sources provided.
| Definition: | Source: |
|---|---|
| A measure of the existence, completeness, quality, and documentation of data standards, data models, business rules, metadata, and reference data. | D. McGilvray, “Executing Data Quality Projects: Ten Steps to Quality Data and Trusted Information”, Morgan Kaufmann Publishers, 2008. |
| The data element has a commonly agreed upon enterprise business definition and calculations. | B. BYRNE, J. K., D. MCCARTY, G. SAUTER, H. SMITH, P WORCESTER 2008. The information perspective of SOA design Part 6:The value of applying the data quality analysis pattern in SOA. IBM corporation. |
| SIGNS AND OTHER Information-Bearing Mechanisms like Traffic Signals should be standardized and universally used across the broadest audience possible. | ENGLISH, L. P. 2009. Information quality applied: Best practices for improving business information, processes and systems, Wiley Publishing. |
| Validity of data refers to data that has been collected in accordance with any rules or definitions that are applicable for that data. This will enable benchmarking between organisations and over time. | HIQA 2011. International Review of Data Quality Health Information and Quality Authority (HIQA), Ireland. http://www.hiqa.ie/press-release/2011-04-28-international-review-data-quality. |